docs-starlight/src/content/docs/02-features/10-hooks.md (5)

232-236: Polish the “Hook exit codes” section: fix typos and tighten phrasing

• Replace “apply more control to” with “control”/“gain more control over.”
• Fix “after-hook” → “after_hook.”
• Remove the stray “the” and extra backtick.
• Avoid “unit” (undefined term here); use “configuration” (or “module/directory”) for clarity.

-Hooks allow you to apply more control to the exit code returned by the applicable underlying OpenTofu/Terraform command. If any `before_hook` or `after_hook` returns a non-zero exit code, the Terragrunt command you run against the unit will return a non-zero exit code.
+Hooks let you control Terragrunt's exit code. If any `before_hook` or `after_hook` returns a non-zero exit code, the Terragrunt command will exit non-zero.

-For example, suppose you run `terragrunt apply` on a given unit that has no `before_hook`, but has a non-empty `after-hook`. Because there is no `before_hook` defined, Terragrunt will first run `tofu apply`, and let's assume that succeeds and returns an exit code of `0`. Next, Terragrunt will run your `after_hook`. If that fails and returns an exit code of `1`, the ` the entire `terragrunt apply` operation will return an exit code of `1`, even though the underlying `tofu apply` succeeded.
+For example, suppose you run `terragrunt apply` in a configuration that defines no `before_hook` but does define an `after_hook`. Terragrunt will first run `tofu apply` (assume it succeeds and returns `0`). Next, Terragrunt runs the `after_hook`. If that hook fails and returns `1`, the overall `terragrunt apply` command will also return `1`, even though `tofu apply` succeeded.

---

9-11: Capitalize “Terragrunt” and fix article usage

Minor grammar/consistency nits.

-_Before Hooks_, _After Hooks_ and _Error Hooks_ are a feature of terragrunt that make it possible to define custom actions that will be called before/after running an `tofu`/`terraform` command.
+_Before Hooks_, _After Hooks_, and _Error Hooks_ are a feature of Terragrunt that make it possible to define custom actions that will be called before/after running a `tofu`/`terraform` command.

---

132-136: Smoother wording

Tighten the sentence and clarify “related to running OpenTofu/Terraform.”

-Hooks can be used to handle operations that need to happen, but are not directly related to the OpenTofu/Terraform.
+Hooks can handle operations that need to happen but are not directly related to running OpenTofu/Terraform.

---

209-211: Subject–verb agreement and concision

“Each hook … they are” mismatch; also simplify phrasing.

-You can have multiple before and after hooks. Each hook will execute in the order they are defined.
+You can define multiple before and after hooks. Each hook executes in the order it is defined.

---

255-257: Fix possessive “its” and parallelism

Also capitalize the product name consistently in the link text if you prefer.

-The `.tflint.hcl` should exist in the same folder as `terragrunt.hcl` or one of it's parents. If Terragrunt can't find
-a `.tflint.hcl` file, it won't execute tflint and return an error. All configurations should be in a `config` block in this
-file, as per [Tflint's docs](https://github.com/terraform-linters/tflint/blob/master/docs/user-guide/config.md).
+The `.tflint.hcl` should exist in the same folder as `terragrunt.hcl` or one of its parents. If Terragrunt can't find
+a `.tflint.hcl` file, it won't execute tflint and will return an error. All configurations should be in a `config` block in this
+file, as per [TFLint's docs](https://github.com/terraform-linters/tflint/blob/master/docs/user-guide/config.md).

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.